-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix example of topologySpreadConstraints to reference trust-manager #401
Conversation
Signed-off-by: Ashley Davis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
/approve
/lgtm
/hold so that you can read my comment
@@ -167,8 +167,7 @@ tolerations: [] | |||
# whenUnsatisfiable: ScheduleAnyway | |||
# labelSelector: | |||
# matchLabels: | |||
# app.kubernetes.io/instance: cert-manager | |||
# app.kubernetes.io/component: controller | |||
# app.kubernetes.io/name: trust-manager |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This single label selector is equivalent but not identical to the single label selector in the Deployment selector:
trust-manager/deploy/charts/trust-manager/templates/deployment.yaml
Lines 11 to 12 in ee9a7b6
matchLabels: app: {{ include "trust-manager.name" . }}
I guess its better practice to use this namespaced label.
And I guess the reason for removing the app.kubernetes.io/instance
label is that there must only be one instance of trust-manager in each cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly, I didn't think that deeply on this. Topology spread constraints are pretty deep into K8s magic land, and I reckon anyone wanting to set them is probably pretty comfortable with label selectors and picking what they want - I just wanted an example which mentioned trust-manager, really!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wallrj The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold I think the question has been seen! |
Spotted by @wallrj in cert-manager/istio-csr#365